Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow unsafe-eval to fix font renderer in Chromium extension #4738

Merged
merged 1 commit into from
May 9, 2014
Merged

Allow unsafe-eval to fix font renderer in Chromium extension #4738

merged 1 commit into from
May 9, 2014

Conversation

Rob--W
Copy link
Member

@Rob--W Rob--W commented May 5, 2014

Fixes #4660

@yurydelendik
Copy link
Contributor

I can accept this solution for now until we are looking for better solution for #4660

@timvandermeij
Copy link
Contributor

I have verified this fix with the Chrome documentation and by building and testing the extension itself. Let's merge this, but keep the original issue open to find a better solution later.

timvandermeij added a commit that referenced this pull request May 9, 2014
@timvandermeij
Merge pull request #4738 from Rob--W/allow-unsafe-eval
dc214e1 
Allow unsafe-eval to fix font renderer in Chromium extension
@timvandermeij timvandermeij merged commit dc214e1 into mozilla:master May 9, 2014
@timvandermeij
Copy link
Contributor

Thank you!

@timvandermeij timvandermeij mentioned this pull request May 9, 2014
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Font renderer logic violates the Content security policy (no unsafe-eval)
3 participants
@Rob--W @yurydelendik @timvandermeij